Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Bump ORA version to 0.2.7. #11429

Merged
merged 1 commit into from
Feb 5, 2016
Merged

Bump ORA version to 0.2.7. #11429

merged 1 commit into from
Feb 5, 2016

Conversation

cahrens
Copy link

@cahrens cahrens commented Feb 4, 2016

No description provided.

@@ -78,7 +78,7 @@ git+https://github.com/edx/XBlock.git@xblock-0.4.4#egg=XBlock==0.4.4
-e git+https://github.com/edx/event-tracking.git@0.2.1#egg=event-tracking==0.2.1
-e git+https://github.com/edx/django-splash.git@v0.2#egg=django-splash==0.2
-e git+https://github.com/edx/acid-block.git@e46f9cda8a03e121a00c7e347084d142d22ebfb7#egg=acid-xblock
-e git+https://github.com/edx/edx-ora2.git@0.2.6#egg=ora2==0.2.6
-e git+https://github.com/edx/edx-ora2.git@0.2.7#egg=ora2==0.2.7
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Now would be a fine time to remove the -e.

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@nedbat
What does it mean to remove the "-e"? Why was it there before, and why do we no longer need it?

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The -e means, install as an editable working tree. We never needed it, it's been cargo-culted from the beginning. It's allowed us to have bugs in our setup.py files that we don't find until much later.

The instructions at the top of the file were an attempt to get people to stop using it. :)

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@nedbat thanks. I would think you knew by now that nobody reads the instructions at the top of the file (unless the thing they are changing is at the top of the file). :)

@cahrens
Copy link
Author

cahrens commented Feb 4, 2016

jenkins run bokchoy

@nedbat
Copy link
Contributor

nedbat commented Feb 4, 2016

The test failures are because of the errors in ora's setup.py: it doesn't name all of the packages that it should.

@cahrens
Copy link
Author

cahrens commented Feb 5, 2016

Thanks, @nedbat. So does ora2 need to declare EVERY package it has? Is there no concept of "private" packages?

For instance, there is an init file in openassessment/assessment/migrations, but it seems odd to declare that as a package.

See openedx/edx-ora2#865

@nedbat
Copy link
Contributor

nedbat commented Feb 5, 2016

If you want the code to be installed when the kit is installed, then it needs to be in the packages list. That's all that list is for: what packages are in the kit, and need to be copied during installation. Many people avoid an explicit list of packages by doing this:

from setuptools import find_packages
...
setup(
    ....
    packages=find_packages(),
    ...
)

Some people exclude certain packages, but there it isn't required.

@cahrens
Copy link
Author

cahrens commented Feb 5, 2016

jenkins run lettuce

@cahrens
Copy link
Author

cahrens commented Feb 5, 2016

jenkins run bokchoy

cahrens pushed a commit that referenced this pull request Feb 5, 2016
@cahrens cahrens merged commit 481f322 into master Feb 5, 2016
@cahrens cahrens deleted the christina/ora-release branch February 5, 2016 16:14
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants